POV-Ray : Newsgroups : povray.windows : NO whitespaces allowed in Path to ini ? : Re: NO whitespaces allowed in Path to ini ? Server Time
5 Jul 2024 04:54:45 EDT (-0400)
  Re: NO whitespaces allowed in Path to ini ?  
From: Theo Gottwald *
Date: 15 Aug 2002 00:42:16
Message: <3d5b3128@news.povray.org>
Yes, ... they say its because of the Win2k-shell.
One person reports that he can do it under WinNT.

However due to these problems SMPOV (www.it-berater.org/smpov.htm )
has a text-file which say that you have to avoid pathes with whitespaces.

(In fact Pandora is right - we are not 100% shure why it does not work here
on my PC's ...)

--Theo

"Pandora" <pan### [at] pandora-softwarecom> schrieb im Newsbeitrag
news:3d5b07e0@news.povray.org...
> "Ken" <tyl### [at] pacbellnet> wrote in message
> news:3D5AFC2D.6C2F62D7@pacbell.net...
> >
> >
> > Theo Gottwald * wrote:
> > >
> > > I did that, they have been in Quotation marks (=chr$(34) - isn't ?).
> >
> > Quotation marks - ""
> >
>
>
>     The point Theo is trying to make, and is actually quite clear from his
> original post, is that the parameter _was_ in Quotation marks. chr$(34),
as
> Theo puts it, _is_ a quotation mark. To quote from Theos original question
:
>
> "The following Line in a batch file:
>
> bin\pvengine.exe "f:\00_rpgm\01_bs\01_projekte\smpov
> 1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini"
>
> Please note the chr$(34) (=") around the path."
>
> See, he even makes a point of stating that he is using quotation marks
> around the file path parameter.
>
> So, Theos original question still stands - why does this not work ?
> --
> Pandora/Scott Hill/[::O:M:C::]Scorpion
> Software Engineer.
> http://www.pandora-software.com
>
>


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.